Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues/8607/review missed #9259

Closed

Conversation

Sancharisingh
Copy link

@Sancharisingh Sancharisingh commented Nov 30, 2024

Proposed Changes

  • Fixes Review Missed #8607
  • Change 1: In the ManagePatients.tsx file, I added a condition that displays:
    Time left for review if the review is upcoming.
    Missed since [X] days if the review time has passed
  • Change 2
  • More?

@ohcnetwork/care-fe-code-reviewers

Merge Checklist

  • Add specs that demonstrate bug / test a new feature.
  • Ensure that UI text is kept in I18n files.
  • Update product documentation.
  • Prep screenshot or demo video for changelog entry, and attach it to issue.
Screenshot 2024-11-30 at 8 02 25 PM
  • Request for Peer Reviews
  • Completion of QA

Summary by CodeRabbit

  • New Features
    • Enhanced patient review notifications with clear indicators for missed ("Review Missed") and upcoming ("Review Due in") reviews, improving user awareness.
    • Improved phone number management with validation for primary and emergency contact numbers.
    • Refactored search functionality to allow searching by patient name, IP/OP number, and phone numbers using new input components.
    • Introduced a new Badge component with additional styling variants, including a new "success" variant, for improved visual clarity and accessibility.
  • Bug Fixes
    • Streamlined code by removing unnecessary commented-out sections, improving maintainability.

@Sancharisingh Sancharisingh requested a review from a team as a code owner November 30, 2024 14:33
Copy link
Contributor

coderabbitai bot commented Nov 30, 2024

Walkthrough

The changes in this pull request update the ManagePatients.tsx component to enhance the handling and display of patient information, particularly for phone number management and review notifications. New state variables for phone numbers have been added with validation logic. The notification display has been improved to show dynamic badges indicating review status. Additionally, the search functionality has been refactored for better usability, while the overall component structure remains unchanged.

Changes

File Path Change Summary
src/components/Patient/ManagePatients.tsx Enhanced phone number management and validation; improved review notification display with dynamic badges; refactored search functionality.
src/components/ui/badge.tsx Introduced a new Badge component with styling variants for dynamic notifications.

Assessment against linked issues

Objective Addressed Explanation
Enable user to understand when a review was missed (8607)
Allow sorting by duration since review is missed (8607) No implementation for sorting functionality.
Display relative time since review missed (8607)

Possibly related PRs

Suggested labels

needs review, tested, P1

Suggested reviewers

  • rithviknishad
  • Jacobjeevan

🐰 "In the garden where patients dwell,
Notifications ring like a gentle bell.
Missed reviews now clearly show,
Days gone by, and due dates flow.
With each chip, a tale to tell,
Clarity blooms, all is well!" 🐇


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between b77f123 and c6e8d75.

📒 Files selected for processing (1)
  • src/components/ui/badge.tsx (1 hunks)
🧰 Additional context used
🪛 eslint
src/components/ui/badge.tsx

[error] 15-16: Delete

(prettier/prettier)

🔇 Additional comments (4)
src/components/ui/badge.tsx (4)

6-13: LGTM! Well-documented component with relevant examples.

The documentation clearly explains the component's purpose and includes practical examples specifically demonstrating the review status use cases, which aligns well with the PR objectives.


16-38: LGTM! Well-structured variants with semantic colors.

The variant definitions are well-thought-out:

  • Purple variant for "Review Missed" provides good visual distinction
  • Success variant for upcoming reviews follows conventional color semantics
  • Base styles include proper focus states for accessibility

40-53: LGTM! Clean implementation with proper accessibility.

The component implementation successfully incorporates the previously suggested accessibility improvements, including proper ARIA attributes and TypeScript types.


1-56: Verify integration with ManagePatients component.

The Badge component looks well-implemented for the review status feature. Let's verify its integration:

✅ Verification successful

Badge component is correctly integrated with ManagePatients.tsx

The Badge component is properly integrated and used as intended:

  • Uses "purple" variant for missed reviews with "Review Missed X days ago" text
  • Uses "success" variant for upcoming reviews with "Review Due in X days" text
  • Includes proper conditional rendering based on review_time and consultation status
  • Implements the exact visual distinction specified in the component's documentation
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check Badge component usage in ManagePatients.tsx
# Expect to find usage with 'purple' variant for missed reviews and 'success' for upcoming reviews

# Search for Badge usage in ManagePatients.tsx
rg -A 2 "Badge.*variant=[\"\'](?:purple|success)" "src/components/Patient/ManagePatients.tsx"

Length of output: 217


Script:

#!/bin/bash
# Let's try a simpler search first to find any Badge usage
rg -l "Badge" "src/components/Patient/ManagePatients.tsx"

# Also search for Badge imports
rg "import.*Badge" "src/components/Patient/ManagePatients.tsx"

# Let's also check if ManagePatients.tsx exists in a different location
fd -t f "ManagePatients.tsx"

Length of output: 334


Script:

#!/bin/bash
# Now that we confirmed the file exists and imports Badge, let's look for its usage
rg -A 3 "<Badge" "src/components/Patient/ManagePatients.tsx"

# Also check for any variant prop usage with Badge
rg -A 3 "Badge.*variant=" "src/components/Patient/ManagePatients.tsx"

# Let's also check the entire component to understand the review status context
rg -A 5 "review.*status|status.*review" "src/components/Patient/ManagePatients.tsx" -i

Length of output: 382


Script:

#!/bin/bash
# Let's get more context around the Badge usage we found
rg -B 2 -A 5 "<Badge" "src/components/Patient/ManagePatients.tsx"

# Also search for any review-related logic near the Badge
rg -B 5 -A 5 "review_time" "src/components/Patient/ManagePatients.tsx"

Length of output: 1736

🧰 Tools
🪛 eslint

[error] 15-16: Delete

(prettier/prettier)


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

netlify bot commented Nov 30, 2024

Deploy Preview for care-ohc ready!

Name Link
🔨 Latest commit c6e8d75
🔍 Latest deploy log https://app.netlify.com/sites/care-ohc/deploys/67567be674c5d90008c8af8f
😎 Deploy Preview https://deploy-preview-9259--care-ohc.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Outside diff range and nitpick comments (1)
src/components/Patient/ManagePatients.tsx (1)

642-658: Consider using i18n for review notification text

The implementation nicely handles both missed and upcoming reviews with clear time indicators. However, the text strings should be internationalized for consistency.

Consider using i18n translations:

-                            ? `Review Missed (${Math.abs(dayjs().diff(dayjs(patient.review_time), "days"))} days ago)`
-                            : `Review Due in (${Math.abs(dayjs(patient.review_time).diff(dayjs(), "days"))} days)`
+                            ? t("review_missed_days_ago", {
+                                days: Math.abs(dayjs().diff(dayjs(patient.review_time), "days"))
+                              })
+                            : t("review_due_in_days", {
+                                days: Math.abs(dayjs(patient.review_time).diff(dayjs(), "days"))
+                              })
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 8118ccf and b47daad.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (2)
  • package.json (1 hunks)
  • src/components/Patient/ManagePatients.tsx (2 hunks)
🔇 Additional comments (1)
src/components/Patient/ManagePatients.tsx (1)

Line range hint 631-641: LGTM! Good cleanup of commented code.

Removing commented-out code improves code maintainability.

package.json Outdated Show resolved Hide resolved
package.json Outdated
@@ -96,7 +96,7 @@
"tailwind-merge": "^2.5.4",
"tailwindcss-animate": "^1.0.7",
"use-keyboard-shortcut": "^1.1.6",
"xlsx": "^0.18.5"
"xlsx": "https://cdn.sheetjs.com/xlsx-0.20.3/xlsx-0.20.3.tgz"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Sancharisingh this change seems to be unrelated to the linked PR. If you meant to solve #9183, please raise a separate PR solving that alone.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rithviknishad, I’ve removed the changes related to SheetJS. Please review now and let me know if further adjustments are needed.

@@ -628,7 +628,7 @@ export const PatientManager = () => {
)}
</>
)}
{patient.review_time &&
{/* {patient.review_time &&
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove the commented out/old code.

{patient.review_time &&
!patient.last_consultation?.discharge_date &&
Number(patient.last_consultation?.review_interval) > 0 && (
<Chip
Copy link
Contributor

@Jacobjeevan Jacobjeevan Dec 4, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's switch to using Shadcn's Badge here. You can port over the styles from Chip.

Edit: https://github.com/ohcnetwork/care_fe/pull/9138/files#diff-6d99361c2e374eb2dd472d6136d9d5929c8f32128cbb0b6ab8bdafea6beca6ae adds the badge; copy that over and add/adjust variant as necessary.

Copy link
Author

@Sancharisingh Sancharisingh Dec 4, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok 👍

@Jacobjeevan
Copy link
Contributor

Also make sure to edit the title to be human friendly 👍

@Sancharisingh
Copy link
Author

I’ve made the required changes. Should I go ahead and raise a new PR for them, or should I update the existing one instead? Let me know how to proceed.

@github-actions github-actions bot added needs-triage question Further information is requested labels Dec 7, 2024
@rithviknishad
Copy link
Member

update existing PR

@rithviknishad rithviknishad removed question Further information is requested needs-triage labels Dec 7, 2024
@github-actions github-actions bot added the Deploy-Failed Deplyment is not showing preview label Dec 7, 2024
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Outside diff range and nitpick comments (1)
src/components/ui/badge.tsx (1)

6-26: Consider accessibility and contrast improvements.

While the variants are well-defined, consider the following improvements:

  1. The purple variant's hover state in dark mode (dark:hover:bg-purple-800) might have insufficient contrast with the text color (dark:text-purple-200).
  2. Consider adding a success variant for positive states, which would be useful for completed reviews.
 const badgeVariants = cva(
   "inline-flex items-center rounded-md border border-gray-200 px-2.5 py-0.5 text-xs font-semibold transition-colors focus:outline-none focus:ring-2 focus:ring-gray-950 focus:ring-offset-2 dark:border-gray-800 dark:focus:ring-gray-300",
   {
     variants: {
       variant: {
         default:
           "border-transparent bg-gray-900 text-gray-50 shadow hover:bg-gray-900/80 dark:bg-gray-50 dark:text-gray-900 dark:hover:bg-gray-50/80",
         secondary:
           "border-transparent bg-gray-100 text-gray-900 hover:bg-gray-100/80 dark:bg-gray-800 dark:text-gray-50 dark:hover:bg-gray-800/80",
         destructive:
           "border-transparent bg-red-500 text-gray-50 shadow hover:bg-red-500/80 dark:bg-red-900 dark:text-gray-50 dark:hover:bg-red-900/80",
         outline: "text-gray-950 dark:text-gray-50",
         purple:
-          "border-transparent bg-purple-200 text-purple-800 shadow hover:bg-purple-300 dark:bg-purple-900 dark:text-purple-200 dark:hover:bg-purple-800",
+          "border-transparent bg-purple-200 text-purple-800 shadow hover:bg-purple-300 dark:bg-purple-900 dark:text-purple-100 dark:hover:bg-purple-900",
+        success:
+          "border-transparent bg-green-500 text-gray-50 shadow hover:bg-green-500/80 dark:bg-green-900 dark:text-gray-50 dark:hover:bg-green-900/80",
       },
     },
     defaultVariants: {
       variant: "default",
     },
   },
 );
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 0a450f2 and ad568f9.

📒 Files selected for processing (1)
  • src/components/ui/badge.tsx (1 hunks)
🔇 Additional comments (2)
src/components/ui/badge.tsx (2)

1-4: LGTM! Clean and well-organized imports.

The imports follow React best practices and properly separate external and internal dependencies.


1-38: Verify badge variants match all review states.

The component appears well-suited for the PR objectives, supporting both upcoming and missed review states. However, let's verify all required states are covered.

✅ Verification successful

Based on the code review, I can see that the Badge component is used with both "purple" and "destructive" variants for review states in ManagePatients.tsx. Let me verify if all the review states are properly handled.


Badge variants correctly support all review states

The implementation properly handles all review states with appropriate variants:

  • "Review Missed" state uses the purple variant with "X days ago" message
  • "Review Due" state uses the destructive variant with "Due in X days" message

The variants are correctly chosen based on the review time comparison, and the time differences are properly calculated using dayjs for both past and future reviews.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check if ManagePatients.tsx uses appropriate badge variants for all review states

# Search for badge usage in ManagePatients
rg -A 3 "Badge.*variant=" "src/components/Patient/ManagePatients.tsx"

# Search for review-related text to ensure all states are handled
rg "review" "src/components/Patient/ManagePatients.tsx"

Length of output: 638


Script:

#!/bin/bash
# Let's check the actual implementation of badge usage in ManagePatients.tsx to see the variants being used
ast-grep --pattern 'Badge variant=$_'

# Also check for any badge-related JSX elements
rg -l "<Badge" src/components/Patient/ManagePatients.tsx | xargs cat

Length of output: 45147


Script:

#!/bin/bash
# Let's check the review time logic implementation
ast-grep --pattern 'dayjs().isAfter(patient.review_time) ? $_ : $_'

Length of output: 1086

Comment on lines 28 to 38
export interface BadgeProps
extends React.HTMLAttributes<HTMLDivElement>,
VariantProps<typeof badgeVariants> {}

function Badge({ className, variant, ...props }: BadgeProps) {
return (
<div className={cn(badgeVariants({ variant }), className)} {...props} />
);
}

export { Badge, badgeVariants };
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Enhance accessibility and documentation.

The component implementation is clean, but could benefit from improved accessibility and documentation:

+/**
+ * Badge component for displaying status indicators.
+ * @param variant - The visual style variant of the badge
+ * @param className - Additional CSS classes to apply
+ */
 export interface BadgeProps
   extends React.HTMLAttributes<HTMLDivElement>,
     VariantProps<typeof badgeVariants> {}

 function Badge({ className, variant, ...props }: BadgeProps) {
   return (
     <div
+      role="status"
+      aria-label={props['aria-label'] || props.children?.toString()}
       className={cn(badgeVariants({ variant }), className)}
       {...props}
     />
   );
 }

This change:

  1. Adds TypeScript documentation for better developer experience
  2. Adds proper ARIA role for accessibility
  3. Adds aria-label with fallback to child content
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
export interface BadgeProps
extends React.HTMLAttributes<HTMLDivElement>,
VariantProps<typeof badgeVariants> {}
function Badge({ className, variant, ...props }: BadgeProps) {
return (
<div className={cn(badgeVariants({ variant }), className)} {...props} />
);
}
export { Badge, badgeVariants };
/**
* Badge component for displaying status indicators.
* @param variant - The visual style variant of the badge
* @param className - Additional CSS classes to apply
*/
export interface BadgeProps
extends React.HTMLAttributes<HTMLDivElement>,
VariantProps<typeof badgeVariants> {}
function Badge({ className, variant, ...props }: BadgeProps) {
return (
<div
role="status"
aria-label={props['aria-label'] || props.children?.toString()}
className={cn(badgeVariants({ variant }), className)}
{...props}
/>
);
}
export { Badge, badgeVariants };

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)
src/components/ui/badge.tsx (1)

6-10: Enhance component documentation for review status use case.

While the basic documentation is good, consider adding more details about the component's role in displaying review status indicators.

 /**
  * Badge component for displaying status indicators.
  * @param variant - The visual style variant of the badge
  * @param className - Additional CSS classes to apply
+ * @example
+ * // Usage for review status
+ * <Badge variant="destructive">Review Missed</Badge>
+ * <Badge variant="success">Review Due in 2 days</Badge>
  */
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between ad568f9 and e4bb04b.

📒 Files selected for processing (1)
  • src/components/ui/badge.tsx (1 hunks)
🔇 Additional comments (3)
src/components/ui/badge.tsx (3)

12-34: Well-structured variants with appropriate styling.

The badge variants are well-designed with:

  • Appropriate color choices for review status (success/destructive)
  • Consistent dark mode support
  • Proper accessibility features (focus states)

40-49: Implementation matches previous accessibility recommendations.

The current implementation already includes the accessibility improvements suggested in the previous review (role="status" and aria-label).


1-52: Verify integration with review status display requirements.

Let's confirm this component is properly integrated with the review status display requirements.

✅ Verification successful

Badge component is correctly integrated with review status requirements

The verification confirms that the Badge component is properly integrated for displaying review status:

  1. The component is used to show review status with appropriate variants:
    • Uses "purple" variant for "Review Missed" cases
    • Uses "destructive" variant for upcoming reviews
  2. Shows detailed time information:
    • For missed reviews: "Review Missed X days ago"
    • For upcoming reviews: "Review Due in X days"
  3. Only displays for active patients with review intervals > 0 and no discharge date

The implementation aligns with the review status display requirements and uses the Badge component's variants appropriately.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for Badge component usage in ManagePatients.tsx
# Expect to find implementations for both "Review Missed" and "Time left for review" cases

rg -A 5 "Badge.*variant=(\"|\')?(destructive|success)" "src/components/Patient/ManagePatients.tsx"

Length of output: 228


Script:

#!/bin/bash
# Search for Badge component usage in ManagePatients.tsx with fixed regex
rg -A 5 "Badge.*variant" "src/components/Patient/ManagePatients.tsx"

# Also search for Badge imports to verify integration
rg "import.*Badge" "src/components/Patient/ManagePatients.tsx"

# Search for Badge usage across the codebase to understand implementation patterns
rg -A 5 "Badge.*variant" 

Length of output: 661


Script:

#!/bin/bash
# Let's search for actual usage of Badge component in ManagePatients.tsx
rg -l "Badge" "src/components/Patient/ManagePatients.tsx" | xargs cat

# Also search for any review status related code in ManagePatients.tsx
rg -A 5 "review|status" "src/components/Patient/ManagePatients.tsx"

# Search for FilterBadge usage since it's also imported
rg -A 5 "FilterBadge" "src/components/Patient/ManagePatients.tsx"

Length of output: 47572

@Sancharisingh
Copy link
Author

I made the required changes please review my code.

Copy link

github-actions bot commented Dec 9, 2024

👋 Hi, @Sancharisingh,
Conflicts have been detected against the base branch. Please rebase your branch against the base branch.


This message is automatically generated by prince-chrismc/label-merge-conflicts-action so don't hesitate to report issues/improvements there.

@github-actions github-actions bot added the merge conflict pull requests with merge conflict label Dec 9, 2024
@nihal467
Copy link
Member

nihal467 commented Dec 9, 2024

@Jacobjeevan can you look into the PR

Copy link
Contributor

@Jacobjeevan Jacobjeevan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Resolve the merge errors; ensure Manage patients reflects the latest changes.

Your best bet might be to update the file from index and then make your changes once more.

</div>

<SearchByMultipleFields
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Merge error here; SearchByMultipleFields should be included instead of the individual search fields.

const onlyAccessibleFacility =
permittedFacilities?.count === 1 ? permittedFacilities.results[0] : null;

const searchOptions = [
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Merge error; Part of SearchByMultipleFields, and as such should be included.

@Jacobjeevan Jacobjeevan removed needs testing needs review Deploy-Failed Deplyment is not showing preview labels Dec 10, 2024
@Jacobjeevan Jacobjeevan removed their assignment Dec 10, 2024
@github-actions github-actions bot added the stale label Dec 17, 2024
@rithviknishad
Copy link
Member

Closing as stale, feel free to reopen once changes made.

@Sancharisingh
Copy link
Author

Hi @rithviknishad,
I have made the necessary changes. Could you please reopen the PR?
Thank you!

@github-actions github-actions bot added needs-triage question Further information is requested labels Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changes required merge conflict pull requests with merge conflict needs-triage question Further information is requested stale
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Review Missed
4 participants